[NOMERGE] feat: openapi migration progress by ahmed-n-abdeltwab · Pull Request #150 · RocketChat/Rocket.Chat-Open-API

ahmed-n-abdeltwab · 2025-07-17T17:01:56Z

OpenAPI Migration Progress

This PR tracks the ongoing progress of migrating Rocket.Chat API endpoints to the new OpenAPI pattern with AJV validation and improved documentation. It will be continuously updated to reflect completed and remaining work.

✅ Summary

Total endpoints: XX
Migrated so far: 186
Remaining: XX

👥 Team

Ahmed Nasser – Contributor
Matheus Cardoso – Mentor
Guilherme Gazzo – Co-mentor

🚨 Core API Endpoints

These are 500 endpoints critical for core features and should be migrated first:

Authentication (1 / 9 completed)

Content Management (4 / 11 completed)

Integrations (15 / 15 completed)

Marketplace Apps (0 / 4 completed)

apps/public/{app-id}/incoming
apps/public/{appId}/templateMessage
apps
apps/logs

Messaging (8 / 39 completed)

Omnichannel (0 / 154 completed)

Miscellaneous (20 / 34 completed)

Notifications (3 / 7 completed)

banners/{id} chore: Convert some apis to openAPI Rocket.Chat#39265
banners chore: Convert some apis to openAPI Rocket.Chat#39265
banners.dismiss chore: Convert some apis to openAPI Rocket.Chat#39265
banners.getNew
push.get refactor(api): migrate push endpoints to chained API pattern Rocket.Chat#39625
push.info refactor(api): migrate push endpoints to chained API pattern Rocket.Chat#39625
push.token

Rooms (6 / 128 completed)

Settings (39 / 55 completed)

Statistics (0 / 15 completed)

User Management (11 / 54 completed)

Let me know if you'd like these grouped, categorized, or documented further.

📝 Secondary API Endpoints

These 2 endpoints are lower priority and can be migrated after core APIs: (calculating...)

Statistics (0 / 1 completed)

statistics.telemetry ⚠️ Blocked – chore: Add OpenAPI Support to Statistics API Rocket.Chat#35692

⛔ Typia generates oneOf when it encounters a union type (|) in the interface.
The issue with oneOf is that it requires exactly one schema to match—similar to XOR logic—so overlapping types fail validation.
To fix this, we need Typia to generate anyOf instead of oneOf.

User Management (1 / 1 completed)

~~users.getAvatarSuggestion~~ chore: Add OpenAPI Support to users.getAvatarSuggestion API Rocket.Chat#36402

Notifications (7 / 7 completed)

~~push.test~~ chore: Add OpenAPI Support to push.test API Rocket.Chat#36882
calendar-events.list chore: Convert some apis to openAPI Rocket.Chat#39265
calendar-events.info chore: Convert some apis to openAPI Rocket.Chat#39265
calendar-events.create chore: Convert some apis to openAPI Rocket.Chat#39265
calendar-events.import chore: Convert some apis to openAPI Rocket.Chat#39265
calendar-events.update chore: Convert some apis to openAPI Rocket.Chat#39265
calendar-events.delete chore: Convert some apis to openAPI Rocket.Chat#39265

📌 Important Notes

When migrating endpoints to the new OpenAPI + AJV pattern, keep these points in mind:

No Change in Logic
- The migration should only update the structure, validation, and documentation.
- The core business logic, permissions, and side effects must remain exactly the same
Error Response Codes
- 400 (Bad Request) → Should be included for most endpoints with input validation.
- 401 (Unauthorized) → Add only if the endpoint authRequired: true is included.
- 403 (Forbidden) → Add only if specific permission checks are performed.
Schema Validation
- Use AJV for request/response validation.
- Use Typia-generated $ref schemas where available instead of manually defining large object shapes.
Centralized Error Validators
- Use shared helpers like validateBadRequestErrorResponse instead of hard-coding error schemas.
- This keeps error formats consistent across all endpoints.
Route Definition Style
- Use Route Method Chaining when defining multiple methods (.post(), .get(), etc.).
- This is possible because ExtractRoutesFromAPI automatically groups routes under the same path in the type definitions.
Optional Properties
- If an endpoint doesn’t need permissionsRequired, omit it.
- Always explicitly declare query or body in the route options — even if the endpoint has no parameters, set it to query: undefined or body: undefined.
- Keep configs minimal — only include what’s necessary for that endpoint.
No More rest-typings or Manual Typings
- All request/response schemas are now defined directly inside the route definition file.
- No schema definitions in rest-typings or other manual typing files — everything for an endpoint lives in one place for easier maintenance.
Swagger Documentation
- Confirm that both request and response schemas appear correctly in Swagger UI.
- Check that example values are meaningful and match real data structures.

📖 Example: Migrating from Old Pattern to New Pattern

This example shows how to migrate from the legacy addRoute approach (with manual typings and deprecated validation)
to the new typed API definition pattern using:

API.v1.post() / .get() chaining (so multiple HTTP methods for the same path are merged in typings)
AJV for request & response validation
Typia $ref for shared model schemas
Automatic route typings with ExtractRoutesFromAPI (no more manual duplication)
Predefined error response validators instead of hard-coded schemas

Before – Old Pattern

// Route definition
API.v1.addRoute(
	'baz.foo',
	{
		authRequired: true,
		validateParams: ajv.compile<{ name: string }>({ // ❌ Deprecated
				type: 'object',
				properties: { name: { type: 'string' } },
				required: ['name'],
				additionalProperties: false,
			}),
		permissionsRequired: ['manage-foo'],
	},
	{
		async post() {
			const result = await updateFoo(this.bodyParams);
			return API.v1.success(result);
		},
	},
);

API.v1.addRoute(
	'baz.bar',
	{
		authRequired: true,
		validateParams: ajv.compile<{ name: string }>({ // ❌ Deprecated
				type: 'object',
				properties: { name: { type: 'string' } },
				required: ['name'],
				additionalProperties: false,
			}),
		permissionsRequired: ['manage-bar'],
	},
	{
		async get() {
			return API.v1.success(await getBar(this.queryParams.name));
		},
	},
);

// Manual typings in rest-typings
export type BazEndpoint = {
	POST: (params: FooParams) => FooResponse;
    GET: (params: BarParams) => BarResponse;
};

Problems with the old approach:

No request/response schemas → can't generate Swagger/OpenAPI documentation automatically.
validateParams is deprecated → doesn’t integrate with the new pattern.
Manual typings in rest-typings → easy to forget or let them get out of sync.
Hard-coded error handling → duplicated schemas everywhere.

After – New Pattern

const bazEndpoints = API.v1
	// POST /v1/baz.foo
	.post(
		'baz.foo',
		{
			authRequired: true,
			body: ajv.compile<{ name: string }>({
				type: 'object',
				properties: { name: { type: 'string' } },
				required: ['name'],
				additionalProperties: false,
			}),
			permissionsRequired: ['manage-foo'],
			response: {
				400: validateBadRequestErrorResponse, // Common for validation errors
				// 401: validateUnauthorizedErrorResponse, // Optional: if endpoint used with auth
				// 403: validateForbiddenErrorResponse,   // Optional: if specific permission checks exist
				200: ajv.compile<{ foo: IBaz }>({
					type: 'object',
					properties: {
						foo: { $ref: '#/components/schemas/IBaz' }, // ✅ Typia model reuse
						success: { type: 'boolean', enum: [true] },
					},
					required: ['foo', 'success'],
					additionalProperties: false,
				}),
			},
		},
		async function action() {
			const result = await updateFoo(this.bodyParams);
			return API.v1.success(result);
		},
	)
	// GET /v1/baz.bar
	.get(
		'baz.bar',
		{
			authRequired: true,
			query: ajv.compile<{ name: string }>({
				type: 'object',
				properties: { name: { type: 'string' } },
				required: ['name'],
				additionalProperties: false,
			}),
			permissionsRequired: ['manage-bar'],
			response: {
				400: validateBadRequestErrorResponse,
				// 401: validateUnauthorizedErrorResponse, // Optional
				// 403: validateForbiddenErrorResponse,   // Optional
				200: ajv.compile<{ foo: IBaz }>({
					type: 'object',
					properties: {
						bar: { $ref: '#/components/schemas/IBaz' },
						success: { type: 'boolean', enum: [true] },
					},
					required: ['bar', 'success'],
					additionalProperties: false,
				}),
			},
		},
		async function action() {
			return API.v1.success(await getBar(this.queryParams.name));
		},
	);

// ✅ Automatically generate typings for both GET and POST without duplication
export type BazEndpoints = ExtractRoutesFromAPI<typeof bazEndpoints>;

declare module '@rocket.chat/rest-typings' {
    // eslint-disable-next-line @typescript-eslint/naming-convention, @typescript-eslint/no-empty-interface
	interface Endpoints extends BazEndpoints {}
}

Key Improvements in the New Pattern

Single source of truth for typings
ExtractRoutesFromAPI pulls types directly from your post() / get() definitions — no more manual edits in rest-typings.
Strong request validation with AJV
Both body (POST) and query (GET) are validated against JSON schemas.
Strong response validation
Ensures the API always returns objects that match the documented shape.
Reusable schemas with Typia
$ref: '#/components/schemas/IBaz' links to a single IBaz schema used across APIs.
Predefined error validators
validateBadRequestErrorResponse, validateUnauthorizedErrorResponse, validateForbiddenErrorResponse replace repetitive error schemas.
Chaining multiple methods on the same path
Calling .post().get() on the same fooEndpoints ensures both methods are merged into one entry in the generated Endpoints interface.

🧪 Testing Plan

Ensure all migrated endpoints validate request and response schemas using AJV.
Confirm accurate documentation in Swagger UI for each endpoint.
Run integration tests to avoid regressions.

💡 Notes

This PR is for tracking and visibility; implementation PRs will be linked progressively.
Please feel free to suggest changes to prioritization.

CLAassistant · 2025-07-17T17:02:03Z

All committers have signed the CLA.

…ser-management.yaml

Verifieddanny · 2026-02-23T21:31:13Z

Hey @ahmed-n-abdeltwab , I'd like to take on the rooms.leave migration. I don't see any open PR for it. Can I go ahead?

ahmed-n-abdeltwab · 2026-02-23T22:25:28Z

Hey @ahmed-n-abdeltwab , I'd like to take on the rooms.leave migration. I don't see any open PR for it. Can I go ahead?

Please go ahead, but mention this PR so I can mark it yours, because this way no one can duplicate the work

…list endpoint

…endpoint

ahmed-n-abdeltwab · 2026-02-24T14:11:12Z

@Verifieddanny, once your PR is merged, could you please remove your old API like me?

Verifieddanny · 2026-02-24T18:18:24Z

Yes I will 🫡

alchemycodess · 2026-03-14T18:58:37Z

Hi @ahmed-n-abdeltwab , I see there's another PR (#39603) for chat.ignoreUser , should i continue with mine (#39587) or close it?

ahmed-n-abdeltwab · 2026-03-14T19:02:35Z

Hi @ahmed-n-abdeltwab , I see there's another PR (#39603) for chat.ignoreUser , should i continue with mine (#39587) or close it?

We could merged the two PR together but it's recommended if everyone work on deferent API

alchemycodess · 2026-03-14T20:53:02Z

Hi @ahmed-n-abdeltwab , I'd like to migrate chat.getThreadMessages and chat.getDiscussions endpoints to the new OpenAPI + AJV pattern. Can I go ahead?

ahmed-n-abdeltwab · 2026-03-15T02:39:21Z

Hi @ahmed-n-abdeltwab , I'd like to migrate chat.getThreadMessages and chat.getDiscussions endpoints to the new OpenAPI + AJV pattern. Can I go ahead?

ok

NAME-ASHWANIYADAV · 2026-03-15T05:31:29Z

Hi @ahmed-n-abdeltwab, I'd like to claim livechat/analytics/agent-overview and livechat/analytics/overview for migration. Can I go ahead?

ahmed-n-abdeltwab · 2026-03-15T11:10:27Z

Hi @ahmed-n-abdeltwab, I'd like to claim livechat/analytics/agent-overview and livechat/analytics/overview for migration. Can I go ahead?

sure, go ahead

amitb0ra · 2026-03-15T12:55:18Z

Hi @ahmed-n-abdeltwab, I'd like to claim voip/call/{callId}/* for migration. Can I go ahead?

ahmed-n-abdeltwab · 2026-03-15T13:09:32Z

Hi @ahmed-n-abdeltwab, I'd like to claim voip/call/{callId}/* for migration. Can I go ahead?

The Omnichannel APIs is bottom of the list. We should probably migrate the other modules first

amitb0ra · 2026-03-15T13:27:59Z

Hi @ahmed-n-abdeltwab, I'd like to claim voip/call/{callId}/* for migration. Can I go ahead?

The Omnichannel APIs is bottom of the list. We should probably migrate the other modules first

Then can i go for users.create, users.register endpoints?

ahmed-n-abdeltwab · 2026-03-15T13:40:40Z

Hi @ahmed-n-abdeltwab, I'd like to claim voip/call/{callId}/* for migration. Can I go ahead?

The Omnichannel APIs is bottom of the list. We should probably migrate the other modules first

Then can i go for users.create, users.register endpoints?

ok

CodeMatrix1 · 2026-03-15T14:13:07Z

Hello ahmed-n-abdeltwab, just a heads up, My PRs on endpoints chat.search, chat.getDeletedMessages and chat.postMessage are ready to merge, I have resolved all comments etc,

thanks a lot for your spontaneity, really appreciate it!!!

hey @ahmed-n-abdeltwab , I have replied to your questions on my PRs, fyi, thanks a lot for the feedback btw!!

alchemycodess · 2026-03-15T22:18:06Z

Hi @ahmed-n-abdeltwab , I've opened PRs for the following migrations:
chat.getDiscussions - RocketChat/Rocket.Chat#39649
chat.getThreadMessages - RocketChat/Rocket.Chat#39654

smirk-dev · 2026-03-16T10:20:32Z

hi @ahmed-n-abdeltwab you have already reviewed pr RocketChat/Rocket.Chat#39625 (comment) and I have implemented your requested changes, so just leaving this here

sezallagwal · 2026-03-16T16:41:44Z

Hi @ahmed-n-abdeltwab
These PRs have been open for a while:
RocketChat/Rocket.Chat#39349
RocketChat/Rocket.Chat#39350

Could you please review them when you get a chance?

Harxhit · 2026-03-16T18:22:03Z

Hi @ahmed-n-abdeltwab ,

I have completed the migration of two endpoints to the typed REST API structure:

chat.syncThreadMessages
refactor(chat): migrate chat.syncThreadMessages to typed REST endpoint Rocket.Chat#39669
chat.getThreadsList
refactor(chat): migrate chat.getThreadsList to typed REST endpoint Rocket.Chat#39655

Both endpoints are now aligned with the typed REST endpoint pattern used across the codebase. I have resolved the conflicts, and everything looks correct from my side.

Whenever you have time, could you please review them?
Thanks.

ahmed-n-abdeltwab · 2026-03-16T19:05:13Z

Hi @ahmed-n-abdeltwab ,

I have completed the migration of two endpoints to the typed REST API structure:

chat.syncThreadMessages
refactor(chat): migrate chat.syncThreadMessages to typed REST endpoint Rocket.Chat#39669

chat.getThreadsList
refactor(chat): migrate chat.getThreadsList to typed REST endpoint Rocket.Chat#39655

Both endpoints are now aligned with the typed REST endpoint pattern used across the codebase. I have resolved the conflicts, and everything looks correct from my side.

Whenever you have time, could you please review them? Thanks.

no it's not completed yet, you still need to complete the other steps

smirk-dev · 2026-03-16T19:09:36Z

hi @ahmed-n-abdeltwab you have already reviewed pr RocketChat/Rocket.Chat#39625 (comment) and I have implemented your requested changes, so just leaving this here

@ahmed-n-abdeltwab can you also checkout issue RocketChat/Rocket.Chat#38876

Harxhit · 2026-03-16T19:23:25Z

Hi @ahmed-n-abdeltwab ,

I have completed the migration of two endpoints to the typed REST API structure:

chat.syncThreadMessages
refactor(chat): migrate chat.syncThreadMessages to typed REST endpoint Rocket.Chat#39669

chat.getThreadsList
refactor(chat): migrate chat.getThreadsList to typed REST endpoint Rocket.Chat#39655

Both endpoints are now aligned with the typed REST endpoint pattern used across the codebase. I have resolved the conflicts, and everything looks correct from my side.

Whenever you have time, could you please review them? Thanks.

no it's not completed yet, you still need to complete the other steps

Hi @ahmed-n-abdeltwab

Thanks for the feedback. Could you please clarify which remaining steps I should complete for these migrations?

So far I have:

Converted the routes to the typed API pattern (.get / .post chaining)
Added query/body validators with AJV
Added response validation (including success field)
Included 400 and 401 error validators
Verified the endpoint behavior locally

Please let me know what additional steps are still missing so I can complete them.

CodeMatrix1 · 2026-03-16T19:26:15Z

@ahmed-n-abdeltwab can I claim users.delete and users.getUsernameSuggestion?, I see no PRs

ahmed-n-abdeltwab · 2026-03-16T19:39:42Z

@ahmed-n-abdeltwab can I claim users.delete and users.getUsernameSuggestion?, I see no PRs

i suggest you should first compete what you have claim, until that you could move to the next API. make sure that's your old PRs are really ready and migrated completely

ahmed-n-abdeltwab · 2026-03-16T19:45:06Z

Hi @ahmed-n-abdeltwab

Thanks for the feedback. Could you please clarify which remaining steps I should complete for these migrations?

So far I have:

Converted the routes to the typed API pattern (.get / .post chaining)

Added query/body validators with AJV

Added response validation (including success field)

Included 400 and 401 error validators

Verified the endpoint behavior locally

Please let me know what additional steps are still missing so I can complete them.

read the Important Notes number 7, or take a look at the example

7- No More rest-typings or Manual Typings

All request/response schemas are now defined directly inside the route definition file.

No schema definitions in rest-typings or other manual typing files — everything for an endpoint lives in one place for easier maintenance.

CodeMatrix1 · 2026-03-16T20:44:08Z

@ahmed-n-abdeltwab can I claim users.delete and users.getUsernameSuggestion?, I see no PRs

i suggest you should first compete what you have claim, until that you could move to the next API. make sure that's your old PRs are really ready and migrated completely

like I have commented on what u hv asked on chat.getDeletedMessages and chat.postMessage, I do strongly believe my two PRs other than postMessage are ready to merge, i checked out the ui as well its working as expected

Harxhit · 2026-03-17T07:59:23Z

Hi,@ahmed-n-abdeltwab

I have completed the migration of two endpoints to the typed REST API structure:
chat.syncMessages
RocketChat/Rocket.Chat#39682

Whenever you have time, could you please review them? If any changes needed I will fix it.

Harxhit · 2026-03-17T08:03:48Z

Hi @ahmed-n-abdeltwab
Thanks for the feedback. Could you please clarify which remaining steps I should complete for these migrations?
So far I have:

Converted the routes to the typed API pattern (.get / .post chaining)

Added query/body validators with AJV

Added response validation (including success field)

Included 400 and 401 error validators

Verified the endpoint behavior locally

Please let me know what additional steps are still missing so I can complete them.

read the Important Notes number 7, or take a look at the example

7- No More rest-typings or Manual Typings

All request/response schemas are now defined directly inside the route definition file.

No schema definitions in rest-typings or other manual typing files — everything for an endpoint lives in one place for easier maintenance.

Hi @ahmed-n-abdeltwab,

I’ve addressed Note #7 — removed rest-typings and moved all schemas to the route files for both endpoints.

Updated PRs:

chat.syncThreadMessages
refactor(chat): migrate chat.syncThreadMessages to typed REST endpoint Rocket.Chat#39669
chat.getThreadsList
refactor(chat): migrate chat.getThreadsList to typed REST endpoint Rocket.Chat#39655

Please review when you have time.

refactor: remove the webdav from the integrations

34579b4

ahmed-n-abdeltwab added 11 commits July 29, 2025 19:18

refactor: remove pinMessage endpoint from messaging.yaml

ec09975

refactor: remove oauth-apps.create endpoint from integrations.yaml

e29b515

refactor: remove auth-apps.list endpoint from integrations.yaml

2511f83

refactor: remove aoth-apps.delete endpoint from integration

8484c0a

refactor: remove auth-app.update from integration.yaml

da38710

refactor: remove permissions.list, permissions.update endpoint from u…

310412e

…ser-management.yaml

refactor: remove oauth-apps.get endpoint from integration.yaml

b818278

refactor: remove dm.delete endpoint from messaging.yaml

ab7bd56

refactor: remove e2e.setRoomKeyID endpoint from settings.yaml

fe1a149

refactor: remove unPinMessage endpoint from messaging.yaml

f27016e

Merge branch 'main' into feat/openapi

b1cb26e

melohagan mentioned this pull request Jan 14, 2026

Remove Rocket.Chat REST template and logo Budibase/budibase#17749

Merged

ahmed-n-abdeltwab mentioned this pull request Jan 22, 2026

chore: Add OpenAPI Support to chat.getMessage API RocketChat/Rocket.Chat#36819

Open

1 task

ahmed-n-abdeltwab added 2 commits February 23, 2026 21:10

Merge branch 'RocketChat:main' into feat/openapi

0710134

chore(rooms.yaml): Remove deprecated rooms.favorite endpoint

86d8847

Verifieddanny mentioned this pull request Feb 23, 2026

chore: migrate rooms.leave endpoint to new OpenAPI pattern with AJV validation RocketChat/Rocket.Chat#38957

Merged

ahmed-n-abdeltwab added 4 commits February 24, 2026 10:51

chore(content-management.yaml): Remove deprecated custom-user-status.…

ed24359

…list endpoint

chore(miscellaneous.yaml): Remove deprecated commands.get endpoint

2228682

chore(notifications.yaml): Remove deprecated push.test endpoint

56b8c1c

chore(settings.yaml): Remove deprecated e2e.getUsersOfRoomWithoutKey …

06a33b2

…endpoint

alchemycodess mentioned this pull request Mar 13, 2026

chore: migrate chat.getMentionedMessages endpoint to new OpenAPI pattern with AJV validation RocketChat/Rocket.Chat#39616

Open

amitb0ra mentioned this pull request Mar 15, 2026

refactor: Migrate users.create endpoint to OpenAPI with AJV validation RocketChat/Rocket.Chat#39647

Open

This was referenced Mar 15, 2026

chore: migrate chat.getDiscussions endpoint to new OpenAPI pattern with AJV validation RocketChat/Rocket.Chat#39649

Open

chore: migrate chat.getThreadMessages endpoint to new OpenAPI pattern with AJV validation RocketChat/Rocket.Chat#39654

Open

amitb0ra mentioned this pull request Mar 16, 2026

refactor: Migrate users.register endpoint to OpenAPI with AJV validation RocketChat/Rocket.Chat#39676

Open

Merge branch 'main' into feat/openapi

e3df0dc

Conversation

ahmed-n-abdeltwab commented Jul 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

OpenAPI Migration Progress

✅ Summary

👥 Team

🚨 Core API Endpoints

📝 Secondary API Endpoints

📌 Important Notes

📖 Example: Migrating from Old Pattern to New Pattern

Before – Old Pattern

After – New Pattern

🧪 Testing Plan

💡 Notes

Uh oh!

CLAassistant commented Jul 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Verifieddanny commented Feb 23, 2026

Uh oh!

ahmed-n-abdeltwab commented Feb 23, 2026

Uh oh!

ahmed-n-abdeltwab commented Feb 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Verifieddanny commented Feb 24, 2026

Uh oh!

alchemycodess commented Mar 14, 2026

Uh oh!

ahmed-n-abdeltwab commented Mar 14, 2026

Uh oh!

alchemycodess commented Mar 14, 2026

Uh oh!

ahmed-n-abdeltwab commented Mar 15, 2026

Uh oh!

NAME-ASHWANIYADAV commented Mar 15, 2026

Uh oh!

ahmed-n-abdeltwab commented Mar 15, 2026

Uh oh!

amitb0ra commented Mar 15, 2026

Uh oh!

ahmed-n-abdeltwab commented Mar 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

amitb0ra commented Mar 15, 2026

Uh oh!

ahmed-n-abdeltwab commented Mar 15, 2026

Uh oh!

CodeMatrix1 commented Mar 15, 2026

Uh oh!

alchemycodess commented Mar 15, 2026

Uh oh!

smirk-dev commented Mar 16, 2026

Uh oh!

sezallagwal commented Mar 16, 2026

Uh oh!

Harxhit commented Mar 16, 2026

Uh oh!

ahmed-n-abdeltwab commented Mar 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

smirk-dev commented Mar 16, 2026

Uh oh!

Harxhit commented Mar 16, 2026

Uh oh!

CodeMatrix1 commented Mar 16, 2026

Uh oh!

ahmed-n-abdeltwab commented Mar 16, 2026

Uh oh!

ahmed-n-abdeltwab commented Mar 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

CodeMatrix1 commented Mar 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Harxhit commented Mar 17, 2026

Uh oh!

Harxhit commented Mar 17, 2026

Uh oh!

Reviewers

ahmed-n-abdeltwab commented Jul 17, 2025 •

edited

Loading

CLAassistant commented Jul 17, 2025 •

edited

Loading

ahmed-n-abdeltwab commented Feb 24, 2026 •

edited

Loading

ahmed-n-abdeltwab commented Mar 15, 2026 •

edited

Loading

ahmed-n-abdeltwab commented Mar 16, 2026 •

edited

Loading

ahmed-n-abdeltwab commented Mar 16, 2026 •

edited

Loading

CodeMatrix1 commented Mar 16, 2026 •

edited

Loading